System and method of improved large page handling in a virtual memory system

ABSTRACT

A system and method of improved handling of large pages in a virtual memory system. A data memory management unit (DMMU) detects sequential access of a first sub-page and a second sub-page out of a set of sub-pages that comprise a same large page. Then, the DMMU receives a request for the first sub-page and in response to such a request, the DMMU instructs a pre-fetch engine to pre-fetch at least the second sub-page if the number of detected sequential accesses equals or exceeds a predetermined value.

BACKGROUND OF THE INVENTION

1. Technical Field

The present invention relates in general to the field of data processing systems, particularly, memory within data processing systems. Still more particularly, the present invention relates to virtual memory management within data processing systems.

2. Description of the Related Art

Modern data processing systems typically utilize a virtual memory system to address very large amounts of memory, even though the main memory of the system encompasses a much smaller address space. Preferably, virtual memory systems include small storage capacity, rapid access memories (e.g., caches and random-access memory) and large storage capacity, slower access memories (e.g., hard disk drives). To maintain the illusion of a large, addressable memory space, recently-accessed data and instructions are stored in the small storage capacity, rapid access memories. Infrequently-accessed data and instructions are stored in large storage capacity, slower access memories and are only retrieved when requested by a data processing component, such as a processor.

To facilitate the retrieval and access of data within the virtual memory system, data and instructions are typically stored in discrete memory units. Such discrete memory units are typically referred to as “pages”. Because the physical location of a particular memory page may be located in any level of the virtual memory hierarchy, most modern data processing systems transfer or “page” memory pages between various levels of the virtual memory hierarchy as needed. While the various components of the data processing system submit requests to the virtual memory system for required memory pages utilizing a virtual memory address, a page frame table (PFT) is utilized to translate the virtual memory address to an actual physical address of the requested memory page.

Due to their very large size, page frame tables are typically stored in system memory and are often also paged. Those with skill in this art will appreciate that a method of minimizing the cost of main memory access time is to cache recently-accessed page table entries so the page table entry retrieval process is skipped if the current memory page request references the same page as a recently accessed page. Typically, the recently-accessed page table entry is saved in a special translation cache, known to those skilled in this art as a translation lookaside buffer (TLB).

Some modern data processing systems also support large pages to potentially increase memory coverage within the system memory. Such large pages require less memory to store metadata (e.g., page table entries within a page table) for a given memory range. They also require less overhead and can potentially improve performance for applications that have high memory demands. However, large pages may suffer from internal fragmentation, where a large amount of memory within a page is wasted or underutilized. Therefore, there is a need for a system and method for providing for more efficient processing of large memory pages in a data processing system.

SUMMARY OF THE INVENTION

As disclosed, the present invention is a system and method of improved handling of large pages in a virtual memory system. A data memory management unit (DMMU) detects a virtual sequential access of a first sub-page and a second sub-page out of a set of sub-pages that comprise a single large page. Thereafter, the DMMU receives a request for the first sub-page and in response to such a request, the DMMU instructs a pre-fetch engine to pre-fetch at least the second sub-page, if the number of detected sequential accesses exceeds a predetermined value. Those with skill in this art will appreciate that the present invention may also apply to instruction requests controlled by an instruction memory management unit (IMMU).

These and other features and advantages of the present invention will be described in, or will become apparent to those of ordinary skill in the art in view of the following detailed description of the preferred embodiments.

BRIEF DESCRIPTION OF THE FIGURES

The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further objects and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:

FIG. 1 is a block diagram depicting an exemplary data processing system in which a preferred embodiment of the present invention may be implemented;

FIG. 2 is a block diagram illustrating a processor of FIG. 1 in which a preferred embodiment of the present invention may be implemented;

FIG. 3 is a block diagram depicting a multi-tiered translation lookaside buffer (TLB) of FIG. 2 in which a preferred embodiment of the present invention may be implemented;

FIG. 4 illustrates a set of fields in a first-tier TLB entry in which a preferred embodiment of the present invention may be implemented; and

FIG. 5 is a high-level logical flowchart depicting a method of managing virtual memory pages in which a preferred embodiment of the present invention may be implemented.

DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT

With reference now to the figures and in particular, with reference to FIG. 1, there is depicted a block diagram illustrating an exemplary data processing system 100 in which a preferred embodiment of the present invention may be implemented. Exemplary data processing system 100 may be implemented on a general purpose computer, such as one of the members of the IBM-compatible family of computers, or one of several workstation or graphics computer devices which are presently commercially available.

As depicted, exemplary data processing system 100 includes processor(s) 102, which are coupled to system memory 104 via system bus 106. Preferably, system memory 104 may be implemented as a collection of dynamic random access memory (DRAM) modules. Typically, system memory 104 includes data, instructions, and a page frame table (PFT) 116. Mezzanine bus 108 acts as an intermediary between system bus 106 and peripheral bus 114. Those with skill in this art will appreciate that peripheral bus 114 may be implemented as a peripheral component interconnect (PCI), accelerated graphics port (AGP), or any other peripheral bus. Coupled to peripheral bus 114 is hard disk drive 110, which is utilized by data processing system 100 as a mass storage device. Also coupled to peripheral bus 114 are a collection of peripherals 112.

Those skilled in the art will appreciate that data processing system 100 can include many additional components not specifically illustrated in FIG. 1. Because such additional components are not necessary for an understanding of the present invention, they are not illustrated in FIG. 1 or discussed further herein. It should also be understood, however, that the enhancements to data processing system 100 to improve handling of large memory pages provided by the present invention are applicable to data processing systems of any system architecture and are in no way limited to the generalized multi-processor architecture or symmetric multi-processing (SMP) architecture illustrated in FIG. 1.

Referring now to FIG. 2, there is a detailed block diagram illustrating an exemplary processor in which a preferred embodiment of the present invention may be implemented. As shown, processor 102 contains an instruction pipeline including an instruction sequencing unit (ISU) 200 and a number of execution units 208, 212, 214, 218, and 220. ISU 200 fetches instructions for processing from an L1 I-cache 206 utilizing real addresses obtained by the effective-to-real address translation (ERAT) performed by instruction memory management unit (IMMU) 204. Of course, if the requested cache line of instructions does not reside in L1 I-cache 206, then ISU 200 requests the relevant cache line of instructions from L2 cache 234 via I-cache reload bus 207, which is also coupled to a pre-fetch engine 232.

After instructions are fetched and pre-processing, if any, is performed, ISU 300 dispatches instructions, possibly out-of-order, to execution units 208, 212, 214, 218, and 220 via instruction bus 209 based upon instruction type. That is, condition-register-modifying instructions and branch instructions are dispatched to condition register unit (CRU) 208 and branch execution unit (BEU) 212, respectively, fixed-point and load/store instructions are dispatched to fixed-point unit(s) (FXUs) 214 and load-store unit(s) (LSUs) 218, respectively, and floating-point instructions are dispatched to floating-point unit(s) (FPUs) 220.

After possible queuing and buffering, the instructions dispatched by ISU 200 are executed opportunistically by execution units 208, 212, 214, 218, and 220. Instruction “execution” is defined herein as the process by which logic circuits of a processor examine an instruction operation code (opcode) and associated operands, if any and in response, move data or instructions in the data processing system (e.g., between system memory locations, between registers or buffers and memory, etc.) or perform logical or mathematical operations on the data. For memory access (i.e., load-type or store-type) instructions, execution typically includes calculation of a target effective address (EA) from instruction operands.

During execution within one of execution units 208, 212, 214, 218, and 220, an instruction may receive input operands, if any, from one or more architected and/or rename registers within a register file coupled to the execution unit. Data results of instruction execution (i.e., destination operands), if any, are similarly written to instruction-specified locations within the register files by execution units 208, 212, 214, 218, and 220. For example, FXU 214 receives input operands from and stores destination operands to a floating-point register file (FPRP) 222, and LSU 218 receives input operands from GPRF 216 and causes data to be transferred between L1 D-cache 230 (via interconnect 217) and both GPRF 216 and FPRF 222. Similarly, when executing condition-register-modifying or condition-register-dependent instructions, CRU 208 and BEU 212 access control register file (CRF) 210, which in a preferred embodiment includes a condition register, link, register, count register, and rename registers of each. BEU 212 accesses the values of the condition, link, and count registers to resolve conditional branches to obtain a path address, which BEU 212 supplies to instruction sequencing unit 200 to initiate instruction fetching along the indicated path. After an execution unit finishes execution of an instruction, the execution unit notifies instruction sequencing unit 200, which schedules completion of instructions in program order and the commitment of data results, if any, the architected state of processing unit 102.

Still referring to FIG. 2, a preferred embodiment of the present invention preferably includes a data memory management unit (DMMU) 224. DMMU 224 translates effective addresses (EA) in program-initiated load and store operations received from LSU 218 into physical address (PA) utilized the volatile memory hierarchy comprising L1 D-cache 230, L2 cache 234, and system memory 104. DMMU 224 also includes a translation lookaside buffer (TLB) 226.

TLB 226, referenced herein in more detail in conjunction with FIG. 3, buffers copies of a subset of page table entries (PTEs), which are utilized to translate effective addresses (EAs) employed by software executing within processor 102 into physical addresses (PAs). As utilized herein, an effective address (EA) is defined as an address that identifies a memory storage location or other resource mapped to a virtual address space. A physical address (PA), on the other hand, is defined herein as an address within a physical address space that identifies a read memory storage location or other real resource.

Referring now to FIG. 3, there is a more detailed block diagram illustrating TLB 226 of FIG. 2. As illustrated, TLB 226 includes two levels, hereinafter referenced as level-one (L1) TLB 300 and level-two (L2) TLB 302.

As previously discussed, many modern data processing systems support different memory page sizes within the virtual memory system. Larger pages offer advantages such as increased memory coverage in a single page and lower memory requirements for the storage of metadata to describe each memory page. However, memory systems often access only portions of larger pages. These portions are hereinafter referred to as “sub-pages”. Therefore, according to a preferred embodiment of the present invention, DMMU 224 monitors the page reference behavior of an executing application and instructs hardware pre-fetch engine 232 to pre-fetch sub-pages into L1 TLB 300 when another sub-page, contained within the same large page is fetched into L1 TLB 300 on demand, if a number of sequential accesses between the first sub-page and the pre-fetched sub-pages equals or exceeds a pre-determined value. As illustrated in FIG. 3, L1 TLB entries 304 represent sub-pages. For example, L1 TLB entry 304 a represents a first sub-page (SP1) of a second large page (LP2). If a pre-fetched sub-page is the last outstanding sub-page to comprise a large page, DMMU 224 creates an entry in L2 TLB 302 (such as L2 TLB entries 306) for all of the sub-pages that compose the large page.

FIG. 4 illustrates a set of fields in a L1 TLB entry 304 in which a preferred embodiment of the present invention may be implemented. Those with skill in this art will appreciate that each L1 TLB entry 304 can include many additional fields not specifically illustrated in FIG. 4. Because such additional fields are not necessary for an understanding of the present invention, they are not illustrated in FIG. 4 or discussed further herein. As illustrated, each L1 TLB entry 304 includes an identification field 402, data field 404, and a collection of reference counters 406-410.

Identification field 402 preferably includes data identifying L1 TLB entry 304. For example, identification field 402 of L1 TLB entry 304 a includes “SP1, LP2”, which indicates that L1 TLB entry 304 a represents a first sub-page of a second large page stored in L2 TLB 304. Data field 404 preferably includes data stored in the sub-page.

As previously discussed, a large page is comprised of a collection of sub-pages. Therefore, each L1 TLB entry 304 represents a single sub-page in a collection of sub-pages that comprise a large page. A collection of reference counter (RC) entries 406-410 indicate a number of sequential accesses made by DMMU 224 of the current sub-page represented by a L1 TLB entry 304 and subsequent sub-pages. For example, referring back to FIG. 3, if DMMU 224 accesses L1 TLB entry 304 a (which represents sub-page 1 of large page 2) and the next access to a sub-page within the same large page (hereinafter referenced as a “virtual access”) is to a sub-page specified by L1 TLB entry 304 c (which represents sub-page 2 of large page 2), DMMU 224 will increment a value in RC entry 408 of FIG. 4 by one, which indicates a occurrence of a virtual sequential access of L1 TLB entry 304 a and L1 TLB entry 304 c. The operation of RC entries 406-410 will be discussed later in more detail in conjunction with FIG. 5.

With reference to FIG. 5, there is a high-level logical flowchart depicting a method of handling large memory pages in which a preferred embodiment of the present invention may be implemented. The process begins at step 500 and continues to step 502, which illustrates DMMU 224 determining whether a request to reference a sub-page i has been received from a data processing system component. If DMMU 224 determines that a request has not been received, the process iterates at step 502.

However, if DMMU 224 determines that a request has been received, the process continues to step 504, which illustrates DMMU 224 determining whether a TLB entry corresponding to the requested sub-page (sub-page i) is present in L1 TLB 300. If a TLB entry corresponding to the requested sub-page is present in L1 TLB 300, the process continues to step 512, which illustrates DMMU 224 directly accessing a L1 TLB entry 304 corresponding to the requested sub-page and transferring the data to the requesting data processing system element.

Returning to step 504, if DMMU 224 determines that a L1 TLB entry corresponding to the requested sub-page is not present in L1 TLB 300, the process continues to step 506, which illustrates DMMU 224 fetching the requested sub-page and creating a new entry in L1 TLB 300. DMMU 224 accesses page frame table 116, present in system memory 104, to obtain the necessary page table entry to fulfill the memory page request. The process then continues to step 508.

Returning to step 512, after DMMU 224 accesses L1 TLB entry 304 representing the requested sub-page, the process continues to step 508, which illustrates DMMU 224 determining whether L1 TLB entry 304 representing the requested sub-page includes a reference counter (RC) for any other related sub-pages for which the counter equals or exceeds a pre-determined value N. If DMMU 224 determines that a RC corresponding to a related sub-page exists equals or exceeds a pre-determined value N, the process continues to step 510, which illustrates DMMU 224 instructing hardware pre-fetch engine 232 to pre-fetch the sub-page (sub-page j) that corresponds to the RC that equals or exceeds the pre-determined value. The process then continues to step 514.

Returning to step 508, if DMMU 224 determines that no RC corresponding to a related sub-page equals or exceeds a pre-determined value N, the process continues to step 514, which illustrates DMMU 224 determining whether a request to access a sub-page (sub-page j), which corresponds to the same large page as sub-page i, has been received from a data processing component. If DMMU 224 has not received such a request, the process returns to step 502 and proceeds in an iterative fashion. However, if DMMU 224 has received such a request, the process continues to step 516, which illustrates DMMU 224 incrementing RCj for the L1 TLB entry for sub-page i.

Then, the process proceeds to step 518, which illustrates DMMU 224 determining whether requested L1 TLB entry 302 corresponding to sub-page j is present in L1 TLB 300. If sub-page j is present in L1 TLB 300, the process continues to step 520, which illustrates DMMU 224 accessing a L1 TLB entry 304 corresponding sub-page j. The process then returns to step 502 and proceeds in an iterative fashion.

However, returning to step 518, if DMMU 224 determines that the L1 TLB entry 302 corresponding to sub-page j is not present in L1 TLB 300, the process continues to step 522, which illustrates DMMU 224 instruction hardware pre-fetch engine 232 to fetch an L1 TLB entry 302 corresponding to sub-page j from system memory 104. The process then continues to step 520, which depicts DMMU 224 accessing a L1 TLB entry 302 corresponding to sub-page j. Next, RCj for the L1 TLB entry sub-page j is incremented, as depicted in step 524. Other preferred embodiments of the present invention may include only incrementing RCj, as illustrated in step 516, or only incrementing RCi, as depicted in step 524. The process then returns to step 502 and proceeds in an iterative fashion.

As disclosed, the present invention is a system and method of improved handling of large pages in a virtual memory system. A data memory management unit (DMMU) detects a virtual sequential access of a first sub-page and a second sub-page out of a set of sub-pages that comprise a same large page. Then, the DMMU receives a request for the first sub-page and in response to such a request, the DMMU instructs a pre-fetch engine to pre-fetch at least the second sub-page if the number of detected virtual sequential accesses exceeds a predetermined value.

While this invention has been particularly shown as described with reference to a preferred embodiment, it will be understood by those skilled in this art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention. It is also important to note that although the present invention has been described in the context of a fully functional computer system, those skilled in the art will appreciate that the mechanisms of the present invention are capable of being distributed as a program product in a variety of forms, and that the present invention applies equally regardless of the particular type of signal-bearing media utilized to actually carry out the distribution. Examples of such signal-bearing media include, without limitation, recordable-type media such as floppy disks or CD-ROMs and transmission-type media such as analog or digital communication links.

While the invention has been particularly shown and described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention. 

1. A method of data processing, said method comprising: detecting a first access sequence including a first address, second address, and a third address, wherein said first and second addresses belong to a first page and said third address belongs to a second page, wherein a first stride between said first and second addresses do not equal to a second stride between said second and third addresses; determining if a second access sequence accesses a fourth address in said second page immediately after accessing a fifth address in said first page; and in response to said determination, pre-fetching at least said second page out of said plurality of pages upon a third access sequence accessing a sixth address in said first page.
 2. The method according to claim 1, wherein said determining further includes: determining if said second access sequence accesses said fourth address in said second page immediately after accessing a fifth address in said first page, wherein said second address and said fourth address are identical addresses, and wherein said first address and said third address are identical addresses.
 3. The method according to claim 1, wherein said pre-fetching further includes: pre-fetching at least said second page out of said plurality of pages if a number of detected sequential accesses between said first page and said second page equals or exceeds a predetermined value.
 4. A data processing system, comprising: a system memory, including a page frame table; a processor, coupled to said system memory via an interconnect, wherein said process further includes: a first-level cache memory for storing a plurality of sub-pages; a second-level cache memory for storing a plurality of large pages, wherein said plurality of large pages are comprised of a plurality of sub-pages; a pre-fetcher for pre-fetching pages from said page frame table; a data memory management unit for detecting a first access sequence including a first address, second address, and a third address, wherein said first and second addresses belong to a first page and said third address belongs to a second page, wherein a first stride between said first and second addresses do not equal to a second stride between said second and third addresses, determining if a second access sequence accesses a fourth address in said second page immediately after accessing a fifth address in said first page, and in response to said determination, instructing said pre-fetcher to pre-fetch at least said second page out of said plurality of pages upon a third access sequence accessing a sixth address in said first page.
 5. The data processing system according to claim 4, wherein said data memory management unit determines if said second access sequence accesses said fourth address in said second page immediately after accessing a fifth address in said first page, wherein said second address and said fourth address are identical addresses, and wherein said first address and said third address are identical addresses.
 6. The data processing system according to claim 4, wherein said pre-fetcher pre-fetching at least said second page out of said plurality of pages if a number of detected sequential accesses between said first page and said second page equals or exceeds a predetermined value.
 7. A computer program product, comprising: instructions, stored in computer-readable media, for detecting a first access sequence including a first address, second address, and a third address, wherein said first and second addresses belong to a first page and said third address belongs to a second page, wherein a first stride between said first and second addresses do not equal to a second stride between said second and third addresses; instructions, stored in computer-readable media, for determining if a second access sequence accesses a fourth address in said second page immediately after accessing a fifth address in said first page; and instructions, stored in computer-readable media, in response to said determination, for pre-fetching at least said second page out of said plurality of pages upon a third access sequence accessing a sixth address in said first page.
 8. The computer program product according to claim 7, wherein instructions for determining further includes: instructions, stored in computer-readable media, for determining if said second access sequence accesses said fourth address in said second page immediately after accessing a fifth address in said first page, wherein said second address and said fourth address are identical addresses, and wherein said first address and said third address are identical addresses.
 9. The computer program product according to claim 1, wherein said instructions for pre-fetching further includes: instructions, stored in computer-readable media, for pre-fetching at least said second page out of said plurality of pages if a number of detected sequential accesses between said first page and said second page equals or exceeds a predetermined value. 